Skip to content

Remove the private-repo install instructions - #3

Merged
BeLazy167 merged 1 commit into
mainfrom
fix/public-repo-wording
Aug 20, 2026
Merged

Remove the private-repo install instructions#3
BeLazy167 merged 1 commit into
mainfrom
fix/public-repo-wording

Conversation

@BeLazy167

Copy link
Copy Markdown
Member

Follow-up to #2, which merged while the repository was still private.

qBraid/qbraid-code is public now, so three pieces of text are wrong:

  • The README's callout tells people qbraid.com/code.sh "is not live yet" and
    gives a gh api ... contents/install.sh | bash fallback that needs org
    membership. Both URLs are live and anonymous.
  • install.sh and install.ps1 fail a download with "While this repository is
    private you need the GitHub CLI"
    , which now misdiagnoses an outage or a
    dropped connection as a permissions problem.

The gh fallback itself stays — it is a reasonable last resort if both
qbraid.com and raw.githubusercontent.com are unreachable — only the wording
changes.

Verified after the flip

All seven files serve anonymously from raw.githubusercontent.com, and through
the qbraid.com proxy (qbraid-external-site#107):

Path Result
/code.sh, /code.ps1 200, byte-identical to raw
/code/{qbraid-code,statusline.sh,statusline.ps1,doctor.ps1,qbraid-code.cmd} 200, all five
/code/nope, ..%2F..%2Fetc%2Fpasswd 404, inert body
curl <proxy>/code.sh | bash -s -- --help runs
curl <proxy>/code.sh | bash (bad key) reaches the credential step, exits cleanly

shellcheck -S warning and bash -n clean; tests/statusline.sh 12/12.

The repository is public, so qbraid.com/code.sh and /code.ps1 are the only
install path anyone needs. The README still told people to authenticate with
gh and fetch the contents API, and the download error blamed repository
permissions for what is now an ordinary connection failure.
@BeLazy167
BeLazy167 merged commit c488c2c into main Aug 20, 2026
6 checks passed
@BeLazy167
BeLazy167 deleted the fix/public-repo-wording branch August 20, 2026 20:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant